Systems and methods for using on-board resources of individual vehicles in a fleet of vehicles as a distributed data center

ABSTRACT

This disclosure relates to a distributed data center that includes resources carried by a fleet of vehicles. The system includes sensors configured to generate output signals conveying information related to the vehicles. The system may detect vehicle events based on the information conveyed by the output signals. The system includes a remote computing server configured to present a user interface to a user. Through the user interface, the user may query information from one or more vehicles in the fleet. The distributed query is transmitted to individual vehicles, and results are locally processed in accordance with response constraints and subsequently transmitted back to the remote computing server for presentation to the user.

FIELD

The systems and methods disclosed herein are related to using on-boardresources of individual vehicles in a fleet of vehicles as a distributeddata center. In particular, queries and other functions may bedistributed across the fleet. Results from individual vehicles may beaggregated and presented via a user interface to a user of thedistributed data center.

BACKGROUND

Systems configured to record, store, and transmit video, audio, andsensor data associated with a vehicle, e.g. responsive to an accidentinvolving the vehicle, are known. Typically, such systems detect anaccident based on data from a single sensor such as an accelerometer.Some systems store information locally for subsequent analysis. VehicleEngine Control Component (ECM) systems are known. Such systemsinterface/interoperate with external computers (e.g., at an automobilemechanic) where the data stored by the ECM system is analyzed.

SUMMARY

One aspect of the disclosure relates to a system configured to usedata-processing resources carried by a fleet of vehicles as adistributed data center. The fleet of vehicles may include one or moreof a first vehicle, a second vehicle, a third vehicle, and/or a fourthvehicle, and so forth. Individual vehicles may include a set ofresources for data processing and/or electronic storage, including butnot limited to persistent storage. Individual vehicles may include a setof sensors configured to generate output signals conveying informationrelated to the operation of the individual vehicles. As used herein,transmission and/or distribution of information may be considered a dataprocessing function. As used herein, the terms data and information maybe used interchangeably. The system may include sets of resources, setsof sensors, a remote computing server, and/or other components.

One or more components of the system may include one or more processorsand/or other mechanisms/components for processing information. Forexample, a set of resources included in and/or carried by an individualvehicle may include one or more processors. For example, the remotecomputing server may include one or more processors. In someimplementations, other vehicle-specific components, such as, by way ofnon-limiting example, a vehicle event recorder, may include one or moreprocessors. In some implementations, some or all of the processors maybe configured via machine-readable instructions to perform variousfunctions. As used herein, the term “processor” is used interchangeablywith the term “physical processor.”

A set of resources included in and/or carried by an individual vehiclemay include one or more processors, electronic storage, a transceiver,and/or other components. The first vehicle may carry a first set ofresources. The second vehicle may carry a second set of resources, andso forth. The first set of resources may include a first transceiver.The second set of resources may include a second transceiver, and soforth. Transceivers may be configured to transfer and/or receiveinformation to and/or from other elements of the system, including butnot limited to other vehicles (or components carried by other vehicles),the remote computing server, and/or other components. In someimplementations, transceivers may be configured to transfer and/orreceive information wirelessly, and/or otherwise provideinformation-distribution resources. In some implementations,transceivers may be configured to obtain, measure, and/or otherwisedetermine one or more conditions related to data transmissions. Forexample, one or more current local data transmission conditions mayinclude a current bandwidth (e.g., in MB/s), a current transmissionprotocol (e.g., 3G, 4G, LTE, Wi-Fi, etc.), a current transmission cost(e.g., in $/MB), and/or other conditions.

A set of sensors may be configured to generate output signals conveyinginformation. In some implementations, the generated information may berelated to the operation of one or more vehicles. An individual set ofsensors may be carried by an individual vehicle. The generatedinformation may include timing information, operator information, and/orother information. In some implementations, generated information may beassociated with timing information (e.g., from a timer), operatorinformation, and/or other information. In some implementations, timinginformation may associate and/or otherwise relate the generated outputsignals with one or more moments of generation by one or more particularsensors. For example, timing information may include time stamps thatindicate moments of generation. For example, at a time labeled t₁ thespeed of a vehicle may be 50 mph, at a time labeled t₂ the speed may be55 mph, and so forth. A set of time stamps or moments in time may form atimeline. In some implementations, the operator information mayassociate and/or otherwise relate the generated output signals withindividual vehicle operators at the moments of generation. For example,a particular sensor may generate a particular output signal conveying aparticular operating parameter of an individual vehicle, such as speedand/or another operating parameter. The particular output signal mayinclude and/or be associated with a timestamp (e.g., time=t_(x)) thatindicates when the particular output signal was generated. For example,a series of output signals may be associated with a corresponding seriesof timestamps. In some implementations, the particular output signal maybe associated with a particular vehicle operator. For example, theparticular output signal may be associated with the particular vehicleoperator that was operating the individual vehicle at the time theparticular output signal was generated. In some implementations, a setof resources may be configured to store generated information, timinginformation, operator information, and/or other information, e.g. inelectronic storage.

A sensor may be configured to generate output signals conveyinginformation related to the operation and/or one or more operatingconditions of the vehicle. Information related to the operation of thevehicle may include feedback information from one or more of themechanical systems of the vehicle, and/or other information. In someimplementations, at least one of the sensors may be a vehicle systemsensor included in an engine control module (ECM) system or anelectronic control module (ECM) system of the vehicle. In someimplementations, one or more sensors may be carried by the vehicle. Thesensors of a particular vehicle may be referred to as a set of sensors.An individual sensor may be vehicle-specific.

Individual sensors may be configured to generate output signalsconveying information. The information may include visual information,motion-related information, position-related information, biometricinformation, and/or other information. In some implementations, one ormore components of the system may determine one or more parameters thatare measured, derived, estimated, approximated, and/or otherwisedetermined based on one or more output signals generated by one or moresensors.

Sensors may include, by way of non-limiting example, one or more of analtimeter (e.g. a sonic altimeter, a radar altimeter, and/or other typesof altimeters), a barometer, a magnetometer, a pressure sensor (e.g. astatic pressure sensor, a dynamic pressure sensor, a pitot sensor,etc.), a thermometer, an accelerometer, a gyroscope, an inertialmeasurement sensor, global positioning system sensors, a tilt sensor, amotion sensor, a vibration sensor, an image sensor, a camera, a depthsensor, a distancing sensor, an ultrasonic sensor, an infrared sensor, alight sensor, a microphone, an air speed sensor, a ground speed sensor,an altitude sensor, medical sensors (including but not limited to bloodpressure sensor, pulse oximeter, heart rate sensor, etc.),degree-of-freedom sensors (e.g. 6-DOF and/or 9-DOF sensors), a compass,and/or other sensors. As used herein, the term “motion sensor” mayinclude one or more sensors configured to generate output conveyinginformation related to position, location, distance, motion, movement,acceleration, and/or other motion-based parameters. Output signalsgenerated by individual sensors (and/or information based thereon) maybe stored and/or transferred in electronic files. In someimplementations, output signals generated by individual sensors (and/orinformation based thereon) may be streamed to one or more othercomponents of the system.

As mentioned, individual sensors may include image sensors, cameras,and/or other sensors. As used herein, the terms “camera” and/or “imagesensor” may include any device that captures images, including but notlimited to a single lens-based camera, a camera array, a solid-statecamera, a mechanical camera, a digital camera, an image sensor, a depthsensor, a remote sensor, a lidar, an infrared sensor, a (monochrome)complementary metal-oxide-semiconductor (CMOS) sensor, an active pixelsensor, and/or other sensors. Individual sensors may be configured tocapture information, including but not limited to visual information,video information, audio information, geolocation information,orientation and/or motion information, depth information, and/or otherinformation. Information captured by one or more sensors may be marked,timestamped, annotated, and/or otherwise processed such that informationcaptured by other sensors can be synchronized, aligned, annotated,and/or otherwise associated therewith. For example, video informationcaptured by an image sensor may be synchronized with informationcaptured by an accelerometer or other sensor. Output signals generatedby individual image sensors (and/or information based thereon) may bestored and/or transferred in electronic files.

In some implementations, an image sensor may be integrated withelectronic storage such that captured information may be stored, atleast initially, in the integrated embedded storage of a particularvehicle. In some implementations, one or more components carried by anindividual vehicle may include one or more cameras. For example, acamera may include one or more image sensors and electronic storagemedia. In some implementations, an image sensor may be configured totransfer captured information to one or more components of the system,including but not limited to remote electronic storage media, e.g.through “the cloud.”

The system may be coupled to individual vehicles. For example, thesystem may be communicatively coupled to individual vehicles and/or tocomponents carried by individual vehicles, including but not limited totransceivers. For example, components of the system may be configured tocommunicate through one or more networks. The one or more networks may,by way of non-limiting example, include the internet.

The remote computing server may include one or more processors. Theremote computing server may be remote, separate, and/or discrete fromthe fleet of vehicles. The one or more processors may be configured viamachine-readable instructions to perform various functions. The remotecomputing server may be configured to facilitate presentation of a userinterface to a user of the remote computing server. The user interfacemay be configured to facilitate interaction between one or more usersand the remote computing server. For example, the user interface may beconfigured to receive user input from a user. In some implementations,the received input may represent a query, e.g. a distributed query. Thequery may be related to information stored on electronic storage, e.g.in multiple sets of resources of multiple vehicles. Alternatively,and/or simultaneously, the query may be related to one or more vehicleoperators. The remote computing server may be further configured totransmit information based on the query and/or otherwise related to thequery to some vehicles in the fleet or to all vehicles of the fleet.Results and/or other responses from individual vehicles may be received,aggregated, and/or presented by the remote computing server.

In some implementations, a set of resources included in and/or carriedby an individual vehicle may include an event recorder (also referred toas vehicle event recorder). An event recorder may be configured togenerate, detect, identify, capture, and/or record information relatedto operating conditions of a vehicle. Information related to a vehiclemay include, by way of non-limiting example, information related toand/or based on vehicle events. An event recorder may be configured tooff-load and/or otherwise transmit information. In some implementations,an event recorder may include one or more physical processors,electronic storage, and/or other components. In some implementations, anevent recorder may detect vehicle events based on a comparison of theinformation conveyed by the output signals from one or more sensors topredetermined (variable and/or fixed) values, threshold, functions,and/or other information. An event recorder may identify vehicle eventsin real-time or near real-time during operation of a vehicle.

As used herein, the term “vehicle event” may refer to forward motion,motion in reverse, making a turn, speeding, unsafe driving speed,collisions, near-collisions, driving in a parking lot or garage, beingstalled at a traffic light, loading and/or unloading of a vehicle,transferring gasoline to or from the vehicle, and/or other vehicleevents in addition to driving maneuvers such as swerving, a U-turn,freewheeling, over-revving, lane-departure, short following distance,imminent collision, unsafe turning that approaches rollover and/orvehicle stability limits, hard braking, rapid acceleration, idling,driving outside a geo-fence boundary, crossing double-yellow lines,passing on single-lane roads, a certain number of lane changes within acertain amount of time or distance, fast lane change, cutting off othervehicles during lane-change speeding, running a red light, running astop sign, parking a vehicle, performing fuel-inefficient maneuvers,and/or other driving maneuvers. Some types of vehicle events may bebased on the actions or motion of the vehicle itself. Other types ofvehicle events may be based on the actions taken or performed by avehicle operator. Some types of vehicle events may be based on acombination of both the actions or motion of the vehicle itself and theactions taken or performed by a vehicle operator.

The one or more processors of the remote computing server and/or ofindividual sets of resources may be configured to execute one or morecomputer program components. The computer program components may includeone or more of a presentation component, an interface component, adistribution component, a query component, a result component, anaggregate component, a correction component, a re-transmit component, abackup component, a virtualization component, a parameter determinationcomponent, a detection component, a storage component, a derivationcomponent, a virtual sensor component, a memory management component, ascoring component, a conversion component, and/or other components.

The presentation component may be configured to facilitate presentationof user interfaces to users. In some implementations, the presentationcomponent may facilitate presentation of a user interface to a user ofthe remote computing server. In some implementations, the presentationcomponent may facilitate presentation of a user interface to one or morevehicle operators.

The interface component may be configured to facilitate interaction withusers. For example, the interface component may facilitate interactionthrough user interfaces. For example, the interface component mayreceive user input through a user interface. In some implementations,the interface component may receive user input from the user of a remotecomputing server. In some implementations, the received user input mayrepresent a query, e.g., a distributed query. For example, a query maybe related to operation of a fleet of vehicles, one or more vehicleoperators, one or more vehicles, information stored by one or morevehicles, information stored by one or more sets of resources, and/orother information. In some implementations, the query may be related toinformation stored by multiple vehicles, multiple sets of resources,regarding multiple vehicle operators, and/or otherwise distributedinformation that is stored in multiple physical locations. For example,an entire fleet of vehicles may be queried for particular information.For example, an entire fleet of vehicles may be queried for informationmatching one or more criteria and/or filters. In some implementations, aquery may be associated with one or more response constraints.

The distribution component may be configured to transmit informationfrom the remote computing server to all or part of a fleet of vehicles.In some implementations, the distribution component may be configured totransmit information from the remote computing server to all or part ofthe transceivers that are included in and/or carried by a fleet ofvehicles. In some implementations, transmission may be wireless. In someimplementations, transmission may be point-to-point. In someimplementations, transmission may be broadcast. In some implementations,transmission may be bi-directional. For example, the distributioncomponent may be configured to transmit query information from theremote computing server to some or all of the vehicles in a fleet. Queryinformation may be based on a distributed query received from a userinterface. For example, individual transceivers may be configured toreceive the query information transmitted by the distribution component.

The query component may be configured to perform queries. For example,for a particular vehicle, the query component may perform a query onlocally stored information. In some implementations, a distributed querymay be performed on information that is physically stored in multiplelocations. For example, the information may be stored in two, three, ormore vehicles. Subsequent to performance of a distributed query, one ormore sets of (potential) results may be produced, e.g. one set ofresults per vehicle. In some implementations, subsequent data processingmay convert, summarize, adjust, and/or otherwise process potentialresults to create the results that will be transmitted by a transceiver.Individual transceivers may be configured to transmit results fromindividual vehicles to the remote computing server. In someimplementations, performance by the query component may be based on oneor more response constraints, one or more data transmission conditions,and/or other conditions. For example, performance by the query componentmay be based on quality-of-service considerations and/or guidelines.

The conversion component may be configured to convert and/or summarizeone or more potential results into one or more results. For example, theconversion component may be configured to convert a set of potentialresults to create a set of results that will be transmitted by atransceiver. Operation by the conversion component may be based on oneor more response constraints, one or more current local datatransmission conditions, and/or other conditions.

The result component may be configured to receive information from oneor more transceivers. For example, the result component may receive setsof results produced by query components of different vehicles. Forexample, the received information may include a first set of resultsreceived from the transceiver of a first vehicle, a second set ofresults received from the transceiver of a second vehicle, a third setof results received from the transceiver of a third vehicle, and soforth. Individual sets of results may have been produced by individualquery components distributed across different vehicles in the fleet. Forexample, different sets of resources may include individual instances ofa query component.

In some implementations, the result component may be configured toreceive information that has been organized into data packets. Forexample, the data packets may be numbered and/or otherwise annotated. Insome implementations, data packets may include error correctioninformation that may be used to determine, upon receipt, if any of thedata in a set of packets is missing and/or corrupted.

The aggregate component may be configured to aggregate informationreceived from different transceivers. The aggregated information may bereferred to as aggregated results. For example, the aggregate componentmay be configured to aggregate a first set of results from a firsttransceiver, a second set of results from a second transceiver, a thirdset of results from a third transceiver, and so forth. In someimplementations, a particular query performed for a particular vehiclemay produce a zero result, or an empty result. These types of resultsmay be aggregated with the sets of results from other vehicles in afleet. The presentation component may be configured to facilitatepresentation of the aggregated results to a user of the remote computingserver.

The correction component may be configured to determine whether any ofthe data in a set of data packets is missing and/or corrupted. Forexample, a set of data packets may include error correction information(including but not limited to error-checking codes). In someimplementations, a set of received data packets may include annotations,including but not limited to numbering, such that the correctioncomponent can determine whether any data packets are missing. Forexample, the correction component may determine a particular data packetfrom a particular transceiver is missing. For example, the correctioncomponent may determine a different data packet from a differenttransceiver has been corrupted.

The re-transmit component may be configured to transmit requests forparticular information, such as a particular data packet, to one or moretransceivers. Requests from the re-transmit component may be based ondeterminations by the correction component. For example, the re-transmitcomponent may transmit a first request to a particular transceiver forre-transmission of a particular data packet. For example, there-transmit component may transmit a second request to a differenttransceiver for re-transmission of a different data packet. The firstand second request may be based on determinations by the correctioncomponent.

The backup component may be configured to facilitate backup ofparticular information in a separate location such that the particularinformation is physically stored in more than one location. For example,the backup component may select some or all of the information stored inthe set of resources for a particular vehicle. For example, the backupcomponent may select one or more locations suitable for storage that areseparate and remote from the particular vehicle. The selectedinformation may be transmitted to the selected locations for storage.For example, subsequent to operations performed by the backup component,particular information may be stored at different locations. Redundantstorage as accomplished through the operations by the backup componentmay improve the resilience of the fleet of vehicles to localizedoutages, data corruption, loss, and/or other types of accidents.

The virtualization component may be configured to effectuate managementof distributed sets of resources. In some implementations, an individualdistributed set of resources may include resources of the same orsimilar type. For example, a first distributed set of resources mayinclude resources for electronic storage of information, a seconddistributed set of resources may include resources that provideinformation-processing capabilities, a third distributed set ofresources may include resources that provide information-distributioncapabilities, and so forth. For example, the resources for electronicstorage of information may include a first data store (included in thefirst set of resources for the first vehicle), a second data store(included in the second set of resources for the second vehicle), athird data store (included in the third set of resources for the thirdvehicle), and so forth. For example, the virtualization component may beconfigured to manage a distributed data store that includes data storedin the first data store, the second data store, the third data store,and so forth. In some implementations, the virtualization component maybe configured to effectuate management of different layers ofvirtualization of resources. For example, the lowest layer may includethe physical resources, the next layer may include the distributed setsof resources, and the next layer may include distributed APIs,applications, and/or services available to users of the remote computingserver. The API, application, and/or service layer may include supportfor different types and/or formats of queries, and/or for differentoperating systems, e.g. through virtual machines. In someimplementations, the virtualization component may be configured tosupport different types of virtualization, including but not limited toserver virtualization, desktop virtualization, applicationvirtualization, network virtualization, storage virtualization, and/orother types of virtualization.

The parameter determination component may be configured to determinecurrent operating conditions and/or vehicle parameters. The parameterdetermination component may determine current operating conditionsand/or vehicle parameters based on the information conveyed by theoutput signals from the sensors and/or other information. The one ormore current operating conditions may be related to the vehicle, theoperation of the vehicle, physical characteristics of the vehicle,and/or other information. In some implementations, the parameterdetermination component may be configured to determine one or more ofthe current operating conditions one or more times in an ongoing mannerduring operation of the vehicle. In some implementations, the parameterdetermination component may be configured to determine one or more ofthe parameters one or more times in an ongoing manner during operationof the vehicle.

The detection component may be configured to detect vehicle events. Insome implementations, vehicle events may be related to current operatingconditions of a vehicle. For example, a vehicle event may be based oncomparing one or more vehicle parameters with one or more thresholds.

The storage component may be configured to store information inelectronic storage. For example, the information may be stored in theelectronic storage of a particular vehicle. In some implementations, thestored information may be related to detected vehicle events, determinedvehicle parameters, and/or other information. In some implementations,the storage component may be configured to store vehicle event recordsof detected vehicle events in electronic storage.

The derivation component may be configured to determine and/or deriveinformation from other information. For example, the derivationcomponent may be configured to derive a set of derivative operatingconditions from a set of operating conditions that has been determinedby the parameter determination component. For example, a derivativeoperating condition may be a number of occurrences of a particularvehicle event per a time unit. For example, a first derivative operatingcondition may be a number of instances of hard braking per hour ofdrive-time. The definition of “hard braking” may be related to adeceleration meeting a deceleration threshold for a period of timeexceeding a timing threshold. In some implementations, the particulardefinition used to derive a derivative operating condition may bemodified as needed, e.g. by a user of the remote computing server. Asanother example, a derivative operating condition may be a number ofoccurrences of a particular vehicle event per a unit of distancetraveled by a vehicle. For example, a second derivative operatingcondition may be a number of instances of swerving per 100 miles ofdistance traveled by a vehicle. In some implementations, the particulardefinition used to derive a derivative operating condition such asswerving may be modified as needed, e.g. by a user of the remotecomputing server. Derivative operating conditions may include logicaland/or arithmetic combinations of one or more operating conditions. Insome implementations, derivative operating conditions may includecombinations of operating conditions and other derivative operatingconditions.

The virtual sensor component may be configured to define, create, and/orotherwise effectuate management of virtual sensors. A virtual sensor maybe configured to generate an output signal that conveys informationrelated to a derivative operating condition, including but not limitedto derivative operating conditions from the derivation component. Forexample, a first virtual sensor may be defined as a sensor that detectsand/or measures the first derivative operating condition, a secondvirtual sensor may be defined as a sensor that detects and/or measuresthe second derivative operating condition, a third virtual sensor may bedefined as a sensor that detects and/or measures the third derivativeoperating condition, a fourth virtual sensor may be defined as a sensorthat detects and/or measures the fourth derivative operating condition,and so forth. In some implementations, individual derivative operatingconditions may be assigned to individual virtual sensors and/or viceversa. In some implementations, the storage component may be configuredto store output signals generated by virtual sensors (and/or theinformation conveyed thereby) in electronic storage.

The memory management component may be configured to determine and/ormodify rates of store for sensors and/or virtual sensors. For example, afirst sensor may generate output signals continuously conveying a firstoperating parameter. The memory management component may be configuredto determine at what rate the first operating parameter is stored. Forexample, in case the first operating parameter is speed, the rate ofstorage may be once per second, once per 10 seconds, once per minute,and/or another rate of storage. In some implementations, the rate ofstorage may be adjusted based on the occurrence of one or more vehicleevents. For example, some period of time before and/or after aparticular event (such as a collision), the rate of storage may beincreased to a higher rate (e.g., once per second), whereas outside ofthat period of time before and/or after the particular event, the rateof storage may be decreased to a lower rate (e.g., once a minute). Insome implementations, the memory management component may be configuredto allocate previously used storage for reuse. For example, a section ofstorage that was previously used to store a particular operatingparameter at a first rate of storage may be reused partially such that,subsequent to this reuse, the section of storage appears to be used tostore the particular operating parameter at a second rate of storagethat is lower than the first rate of storage. For example, the sectionmay be interleaved with a first set of a first operating parameter(stored at a first rate and generated during a first period) and asecond set of the same operating parameter generated at a second periodsubsequent to the first period. The second set may be stored at the samestorage rate or at a different storage rate. In some implementations,the section may be interleaved with a set of different operatingparameters, which may be stored at the same storage rate, or usingdifferent storage rates.

The scoring component may be configured to determine operator scoresthat are specific to vehicle operators. For example, an operator scoremay reflect a quality assessment of driving by the vehicle operator. Forexample, an operator score may be based on one or more detected vehicleevents. In some implementations, an operator score may include one ormore scores for safety, timeliness, fuel-efficiency, and/or otherdimensions of a quality assessment. In some implementations, an operatorscore may be based on output generated by one or more virtual sensors.In some implementations, operator scores may be presented to vehicleoperators and/or to users of the remote computing server. In someimplementations, operator scores may be stored for future usage.

In some implementations, one or more components of the system may beconfigured to obtain, receive, and/or determine contextual informationrelated to environmental conditions near and/or around vehicles.Environmental conditions may be related to weather conditions, roadsurface conditions, traffic conditions, visibility, and/or otherenvironmental conditions. In some implementations, one or moreenvironmental conditions may be received from one or more sourcesexternal to the vehicle. For example, a source external to the vehiclemay include an external provider.

In some implementations, detection of vehicle events may further bebased one or more types of contextual information. In someimplementations, detection may be accomplished and/or performed at thevehicle.

As used herein, any association (or relation, or reflection, orindication, or correspondency) involving vehicles, sensors, vehicleevents, operating conditions, parameters, thresholds, functions,notifications, constraints, transmission conditions, potential results,results, and/or another entity or object that interacts with any part ofthe system and/or plays a part in the operation of the system, may be aone-to-one association, a one-to-many association, a many-to-oneassociation, and/or a many-to-many association or N-to-M association(note that N and M may be different numbers greater than 1).

As used herein, the term “obtain” (and derivatives thereof) may includeactive and/or passive retrieval, determination, derivation, transfer,upload, download, submission, and/or exchange of information, and/or anycombination thereof. As used herein, the term “effectuate” (andderivatives thereof) may include active and/or passive causation of anyeffect. As used herein, the term “determine” (and derivatives thereof)may include measure, calculate, compute, estimate, approximate,generate, and/or otherwise derive, and/or any combination thereof.

These and other objects, features, and characteristics of the servers,systems, and/or methods disclosed herein, as well as the methods ofoperation and functions of the related elements of structure and thecombination of parts and economies of manufacture, will become moreapparent upon consideration of the following description and theappended claims with reference to the accompanying drawings, all ofwhich form a part of this disclosure, wherein like reference numeralsdesignate corresponding parts in the various figures. It is to beexpressly understood, however, that the drawings are for the purpose ofillustration and description only and are not intended as a definitionof the limits of the invention. As used in the specification and in theclaims, the singular form of “a”, “an”, and “the” include pluralreferents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-2 illustrate systems configured to use data-processing resourcescarried by a fleet of vehicles as a distributed data center, inaccordance with one or more embodiments.

FIG. 3 illustrates an exemplary user interface to be used with a systemconfigured to use data-processing resources carried by a fleet ofvehicles as a distributed data center.

FIG. 4A-4B-4C illustrate a method to use data-processing resourcescarried by a fleet of vehicles as a distributed data center, inaccordance with one or more embodiments.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to use data-processingresources carried by a fleet 12 of vehicles as a distributed datacenter. Fleet 12 may include one or more of a first vehicle, a secondvehicle, a third vehicle, and/or a fourth vehicle, and so forth. As usedhere, the term fleet may refer to a set of at least 5 vehicles, at least10 vehicles, at least 100 vehicles, at least 1000 vehicles, and/oranother number of vehicles. Individual vehicles may include a set ofresources for data processing and/or electronic storage, including butnot limited to persistent storage. Individual vehicles may include a setof sensors configured to generate output signals conveying informationrelated to the operation of the individual vehicles. System 100 mayinclude sets of resources 51, sets of sensors 52, sets of virtualsensors 53, a remote computing server 40, electronic storage 119, and/orother components. In some implementations, system 100 may be or includea distributed data center.

One or more components of system 100 may include one or more processors104 and/or other mechanisms/components for processing information. Forexample, a set of resources 51 included in and/or carried by anindividual vehicle may include one or more processors. For example,remote computing server 40 may include one or more processors. In someimplementations, other vehicle-specific components, such as, by way ofnon-limiting example, a vehicle event recorder, may include one or moreprocessors. In some implementations, some or all of the processors maybe configured via machine-readable instructions to perform variousfunctions. One or more components of system 100 may include electronicstorage 119 and/or other mechanisms/components for storing information.For example, a set of resources 51 included in and/or carried by anindividual vehicle may include electronic storage. For example, remotecomputing server 40 may include electronic storage. In someimplementations, other vehicle-specific components, such as, by way ofnon-limiting example, a vehicle event recorder, may include electronicstorage.

By way of non-limiting example, as shown in FIG. 2, a set of resources51 included in and/or carried by an individual vehicle (e.g. set ofresources 51 c carried by vehicle 12 c) may include one or more ofelectronic storage 70, a processor 71, a transceiver 72, an eventrecorder 73, and/or other components. First vehicle 12 a may carry afirst set of resources 51 a. Second vehicle 12 b may carry a second setof resources 51 b. Third vehicle 12 c may carry a third set of resources51 c, and so forth. First set of resources 51 a may include a firsttransceiver. Second set of resources 51 b may include a secondtransceiver, and so forth. For example, first set of resources 51 a mayinclude first electronic storage, second set of resources 51 b mayinclude second electronic storage, third set of resources 51 c mayinclude third electronic storage (here, storage 70), and so forth. Forexample, first set of resources 51 a may include one or more processors,second set of resources 51 b may include one or more processors, thirdset of resources 51 c may include one or more processors (here,processor 71), and so forth.

Transceivers may be configured to transfer and/or receive information toand/or from other elements of system 100, including but not limited toother vehicles (or components carried by other vehicles in fleet 12),remote computing server 40, and/or other components. In someimplementations, transceivers may be configured to transfer and/orreceive information wirelessly, and/or otherwise provideinformation-distribution resources. In some implementations,transceivers may be configured to obtain, receive, measure, and/orotherwise determine one or more conditions related to datatransmissions. For example, one or more current local data transmissionconditions may include a current bandwidth (e.g., in MB/s), a currenttransmission protocol (e.g., 3G, 4G, LTE, Wi-Fi, etc.), a currenttransmission cost (e.g., in $/MB), and/or other conditions.

Referring to FIG. 1, a set of sensors 52 may be configured to generateoutput signals conveying information. In some implementations, thegenerated information may be related to the operation of one or morevehicles in fleet 12. An individual set of sensors 52 may be carried byan individual vehicle. First vehicle 12 a may carry a first set ofsensors 52 a. Second vehicle 12 b may carry a second set of sensors 52b. Third vehicle 12 c may carry a third set of sensors 52 c, and soforth. The generated information may include timing information,operator information, and/or other information. In some implementations,generated information may be associated with timing information (e.g.,from a timer), operator information, and/or other information. In someimplementations, timing information may associate and/or otherwiserelate the generated output signals with one or more moments ofgeneration by one or more particular sensors. For example, timinginformation may include time stamps that indicate moments of generation.For example, at a time labeled t₁ the speed of a vehicle may be 50 mph,at a time labeled t₂ the speed may be 55 mph, and so forth. A set oftime stamps or moments in time may form a timeline. In someimplementations, the operator information may associate and/or otherwiserelate the generated output signals with individual vehicle operators atthe moments of generation. For example, a particular sensor may generatea particular output signal conveying a particular operating parameter ofan individual vehicle, such as speed and/or another operating parameter.The particular output signal may include and/or be associated with atimestamp (e.g., time=t_(x)) that indicates when the particular outputsignal was generated. For example, a series of output signals may beassociated with a corresponding series of timestamps. In someimplementations, the particular output signal may be associated with aparticular vehicle operator. For example, the particular output signalmay be associated with the particular vehicle operator that wasoperating the individual vehicle at the time the particular outputsignal was generated. In some implementations, a set of resources 51 maybe configured to store generated information, timing information,operator information, and/or other information, e.g. in electronicstorage.

A sensor may be configured to generate output signals conveyinginformation related to the operation and/or one or more operatingconditions of a vehicle. Information related to the operation of avehicle may include feedback information from one or more of themechanical systems of the vehicle, and/or other information. In someimplementations, at least one of the sensors may be a vehicle systemsensor included in an engine control module (ECM) system or anelectronic control module (ECM) system of the vehicle. The sensors of aparticular vehicle may be referred to as a set of sensors. An individualsensor is vehicle-specific.

Information related to current operating conditions of a vehicle mayinclude feedback information from one or more of the mechanical systemsof the vehicle, and/or other information. The mechanical systems of avehicle may include, for example, the engine, the drive train, thelighting systems (e.g., headlights, brake lights), the braking system,the transmission, fuel delivery systems, and/or other mechanicalsystems. The mechanical systems of a vehicle may include one or moremechanical sensors, electronic sensors, and/or other sensors thatgenerate the output signals (e.g., seat belt sensors, tire pressuresensors, etc.). In some implementations, at least one of the sensorscarried by a vehicle may be a vehicle system sensor included in an ECMsystem of the vehicle.

In some implementations, information related to current operatingconditions of a vehicle may include information related to theenvironment in and/or around the vehicle. The vehicle environment mayinclude spaces in and around an interior and an exterior of the vehicle.The information may include information related to movement of thevehicle, an orientation of the vehicle, a geographic position of thevehicle, a spatial position of the vehicle relative to other objects, atilt angle of the vehicle, an inclination/declination angle of thevehicle, and/or other information. In some implementations, the outputsignals conveying information may be generated via non-standardaftermarket sensors installed in the vehicle. Non-standard aftermarketsensors may include, for example, a video camera, a microphone, anaccelerometer, a gyroscope, a geolocation sensor (e.g., a GPS device), aradar detector, a magnetometer, radar (e.g. for measuring distance ofleading vehicle), and/or other sensors. In some implementations, the setof sensors carried by a vehicle may include multiple cameras positionedaround the vehicle and synchronized together to provide a 360-degreeview of the inside of the vehicle (e.g., the cabin) and/or a 360-degreeview of the outside of the vehicle.

Although individual sets of sensors 52 a, 52 b, and 52 c are depicted inFIG. 1 as having three elements, this is not intended to be limiting.For individual vehicles, a set of sensors 142 may include one or moresensors located adjacent to and/or in communication with the variousmechanical systems of the vehicle, in one or more positions (e.g., at ornear the front of the vehicle, at or near the back of the vehicle, onthe side of the vehicle, on or near the windshield of the vehicle,facing outward and/or inward, etc.) to accurately acquire informationrepresenting the vehicle environment (e.g. visual information, spatialinformation, orientation information), and/or in other locations. Forexample, in some implementations, a set of sensors for a particularvehicle may be configured such that a first sensor is located near or incommunication with a rotating tire of the vehicle, and a second sensorlocated on top of the vehicle is in communication with a geolocationsatellite.

Individual sensors may be configured to generate output signalsconveying information. The information may include visual information,motion-related information, position-related information, biometricinformation, and/or other information. In some implementations, one ormore components of system 100 may determine one or more parameters thatare measured, derived, estimated, approximated, and/or otherwisedetermined based on one or more output signals generated by one or moresensors.

Output signals generated by individual sensors (and/or information basedthereon) may be stored and/or transferred in electronic files. In someimplementations, output signals generated by individual sensors (and/orinformation based thereon) may be streamed to one or more othercomponents of system 100.

Individual sensors may include image sensors, cameras, and/or othersensors. Individual sensors may be configured to capture information,including but not limited to visual information, video information,audio information, geolocation information, orientation and/or motioninformation, depth information, and/or other information. Informationcaptured by one or more sensors may be marked, timestamped, annotated,and/or otherwise processed such that information captured by othersensors can be synchronized, aligned, annotated, and/or otherwiseassociated therewith. For example, video information captured by animage sensor may be synchronized with information captured by anaccelerometer or other sensor. Output signals generated by individualimage sensors (and/or information based thereon) may be stored and/ortransferred in electronic files.

System 100 may be coupled to individual vehicles. For example, system100 may be communicatively coupled to individual vehicles and/or tocomponents carried by individual vehicles, including but not limited totransceivers. For example, components of system 100 may be configured tocommunicate through one or more networks 121. The one or more networks121 may, by way of non-limiting example, include the internet.

Remote computing server 40 may include one or more processors 104.Remote computing server 40 may be remote, separate, and/or discrete fromthe fleet of vehicles 12. One or more processors 104 may be configuredvia machine-readable instructions 106 to perform various functions.Remote computing server 40 may be configured to facilitate presentationof a user interface to a user 60 of remote computing server 40. The userinterface may be configured to facilitate interaction between one ormore users and remote computing server 40. For example, the userinterface may be configured to receive user input from user 60. In someimplementations, the received input may represent a query, e.g. adistributed query. The query may be related to information stored onelectronic storage, e.g. in multiple sets of resources of multiplevehicles. Alternatively, and/or simultaneously, the query may be relatedto one or more vehicle operators. Remote computing server 40 may befurther configured to transmit information based on the query and/orotherwise related to the query to some vehicles in the fleet or to allvehicles of the fleet. Results and/or other responses from individualvehicles may be received, aggregated, and/or presented by remotecomputing server 40.

By way of non-limiting example, FIG. 3 illustrates a user interface 80used by user 60 through remote computing server 40. User interface 80may include user interface elements 81 a-81 b-81 c-81 d-82 a-82 b-82c-82 d-83-84 a-84 b-84 c, and/or other elements. For example, selectionelements 81 a, 81 b, 81 c, and 81 d may depict a way for user 60 toenter a distributed query. For example, selection element 81 a includesvehicle operator elements 82 a, which allow user 60 to enter and/orselect up to five vehicle operators, herein labeled as “v1,” “v2,” “v3,”“v4,” and “v5”. For example, selection element 81 b includes event orsensor elements 82 b, which allow user 60 to enter and/or select up tofive vehicle events or sensors, herein labeled as “e1,” “e2,” “e3,”“e4,” and “e5”. For example, selection element 81 c includes timingelements 82 c, which allow user 60 to enter and/or select up to fivetiming periods, herein labeled as “t1,” “t2,” “t3,” “t4,” and “t5”. Forexample, selection element 81 d includes virtual sensor elements 82 d,which allow user 60 to enter and/or select up to five virtual sensors,herein labeled as “vs1,” “vs2,” “vs3,” “vs4,” and “vs5”. For example,first response constraint 84 a may allow user 60 to enter and/or selecta response constraint related to a time frame. For example, secondresponse constraint 84 b may allow user 60 to enter and/or select aresponse constraint related to an amount of data, which may be referredto as a data budget. For example, first response constraint 84 c mayallow user 60 to enter and/or select a response constraint related to anamount of transmission costs. Action element 83 initiates and/orlaunches a distributed query in accordance with the selections and/orentries made in user interface 80.

For example, user interface 80 is configured to let user 60 initiate afirst distributed query of any activity pertaining to a particularvehicle operator. In some cases, a particular vehicle operator may usedifferent vehicles in a span of weeks, months, or years. Relevantinformation pertaining to this vehicle operator may be stored indifferent vehicles. The first distributed query, subsequent toinitiation, may effectuate a search of relevant information amongmultiple vehicles, e.g. among an entire fleet.

For example, a second distributed query may seek a particular type ofactivity (e.g., a particular vehicle event) on a particular vehicle,regardless of which vehicle operators were operating the vehicle at themoment the particular activity occurred.

For example, a third distributed query may seek relevant informationregarding one or more particular types of vehicle events across theentire fleet. For example, such a distributed query may be limited to aparticular period of time, a particular type of weather, a particulargeographical location and/or area, and/or any limitation based on acombination of conditions.

Logical and/or sequential combinations of different types of distributedqueries may be supported. For example, a fourth distributed query mayseek relevant information regarding a particular dangerous drivingmaneuver, at a particular time of day, within a particular geographicalarea, for a particular class of vehicle operators, in particular drivingand/or weather conditions. Any of the distributed queries may beassociated with one or more response constraints. As used herein, aresponse constraint is a vehicle-specific constraint that is used tocontrol operations of an individual set of resources, query component24, conversion component 38, a transceiver, and/or anothervehicle-specific component. A response constraint may limit the amountof data used for a response to a distributed query, the amount of costincurred in providing a response to a distributed query, an amount oftime user to respond to a distributed query, and/or othercharacteristics related to responding to a distributed query, as well aslogical and/or sequential combinations of one or more of these. In someimplementations, vehicle-specific components involved in responding to adistributed query may use a default set of response constraints. Forexample, a particular default constraint may limit responses to $5 indata transmission costs. For example, a particular default constraintmay require responses to be completed in 24 hours from the moment thedistributed query was made. In some implementations, a particulardistributed query my override one or more default response constraints.

Referring to FIG. 2, in some implementations, a set of resourcesincluded in and/or carried by an individual vehicle may include an eventrecorder (also referred to as vehicle event recorder). For example, setof resources 51 c carried by the vehicles may include event recorder 73,as shown in FIG. 2. An event recorder may be configured to generate,detect, identify, capture, and/or record information related tooperating conditions of a vehicle. Information related to a vehicle mayinclude, by way of non-limiting example, information related to and/orbased on vehicle events. An event recorder may be configured to off-loadand/or otherwise transmit information (e.g. through use of a transceiversuch as transceiver 72). In some implementations, an event recorder mayinclude one or more physical processors, electronic storage, and/orother components. In some implementations, an event recorder may detectvehicle events based on a comparison of the information conveyed by theoutput signals from one or more sensors to predetermined (variableand/or fixed) values, threshold, functions, and/or other information. Anevent recorder may identify vehicle events in real-time or nearreal-time during operation of a vehicle.

Referring to FIG. 1, one or more processors 104 of remote computingserver 40 and/or of individual sets of resources 51 may be configured toexecute one or more computer program components. The computer programcomponents may include one or more of a presentation component 21, aninterface component 22, a distribution component 23, a query component24, a result component 25, an aggregate component 26, a correctioncomponent 27, a re-transmit component 28, a backup component 29, avirtualization component 30, a parameter determination component 31, adetection component 32, a storage component 33, a derivation component34, a virtual sensor component 35, a memory management component 36, ascoring component 37, a conversion component 38, and/or othercomponents.

Presentation component 21 may be configured to facilitate presentationof user interfaces to users. In some implementations, presentationcomponent 21 may facilitate presentation of a user interface to user 60of remote computing server 40. In some implementations, presentationcomponent 21 may facilitate presentation of a user interface to one ormore vehicle operators. This enables information to be communicatedbetween a vehicle operator and/or other components of system 100. As anexample, a dangerous driving maneuver and/or vehicle event may bedisplayed to the driver of the vehicle via such a user interface, e.g.as a notification.

Examples of interface devices suitable for inclusion in a user interfaceinclude a keypad, buttons, switches, a keyboard, knobs, levers, adisplay screen, a touch screen, speakers, a microphone, an indicatorlight, an audible alarm, a printer, a tactile feedback device, and/orother interface devices. It is to be understood that other communicationtechniques, either hard-wired or wireless, are also contemplated by thepresent disclosure as a user interface. Other exemplary input devicesand techniques adapted for use by users and/or vehicle operatorsinclude, but are not limited to, an RS-232 port, RF link, an IR link,modem (telephone, cable, and/or other modems), a cellular network, aWi-Fi network, a local area network, and/or other devices and/orsystems. In short, any technique for communicating information iscontemplated by the present disclosure as a user interface.

Interface component 22 may be configured to facilitate interaction withusers. For example, a user may be a fleet manager, or someoneinvestigating fleet operations. Interface component 22 may facilitateinteraction through user interfaces. For example, interface component 22may receive user input through a user interface. In someimplementations, interface component 22 may receive user input from user60 of remote computing server 40. In some implementations, the receiveduser input may represent a distributed query. For example, a distributedquery may be related to one or more vehicle operators, one or morevehicles, information stored by one or more vehicles, information storedby one or more sets of resources, and/or other information. In someimplementations, the distributed query may be related to informationstored by multiple vehicles, multiple sets of resources, regardingmultiple vehicle operators, and/or otherwise distributed informationthat is stored in multiple physical locations. For example, an entirefleet of vehicles 12 (or any subset thereof) may be queried forparticular information. In some implementations, a distributed query maybe associated with one or more response constraints. For example,distribution component 23 may be configured to transmit the one or moreresponse constraints to all or part of fleet of vehicles 12.

In some implementations, distributed queries may be performed onhistoric data, and produce results pertaining to past performance of thefleet of vehicles. In some implementations, distributed queries may beperformed on current data, and produce results pertaining to currentperformance of the fleet of vehicles. A distributed query for currentdata may operate as a subscription on future information that satisfiesthe particular query. In some implementations, distributed queries maybe performed on both historic and current/future data, and producedifferent sets of results for each. For example, different sets ofresponse constraints may be used for historic and current/future data.

In some implementations, interface component 22 may be configured toeffectuate a review presentation to a user or reviewer, e.g. user 60. Areview presentation may be based on information related to one or moredetected vehicle events. In some implementations, a review presentationmay provide a prompt to a user or reviewer to provide manual reviewinput, e.g., regarding one or more detected vehicle events. For example,a reviewer may be prompted via a question, an inquiry, and/or via othertypes of prompts. For example, a reviewer may be asked whether a driverwas wearing a seatbelt at a particular point in time. A reviewpresentation may be implemented as a user interface to facilitateinteraction for a reviewer. For example, such a user interface mayreceive review input from a reviewer, including but not limited tomanual review input. In some implementations, review input may beresponsive to a prompt. In some implementations, a vehicle operator mayreceive information based on review input. Such information may bereferred to as feedback. For example, a user interface for a vehicleoperator (this may be referred to as a driver interface) may present amessage to a vehicle operator to “remember to wear your seatbelt,”responsive to particular review input received from a reviewer (througha different user interface). In some implementations, a driver interfacemay be configured to detect a vehicle operator's response to feedback.In some implementations, the response by a vehicle operator may bespecific to the feedback received through the driver interface.

Distribution component 23 may be configured to transmit information fromremote computing server 40 to all or part of fleet of vehicles 12. Insome implementations, distribution component 23 may be configured totransmit information from remote computing server 40 to all or part ofthe transceivers that are included in and/or carried by fleet ofvehicles 12. In some implementations, transmission may be wireless. Insome implementations, transmission may be point-to-point. In someimplementations, transmission may be broadcast. In some implementations,transmission may be bi-directional. For example, distribution component23 may be configured to transmit wireless query information from remotecomputing server 40 to some or all of the vehicles in fleet 12. Queryinformation may be based on a distributed query received from a userinterface. In some implementations, distribution component 23 may beconfigured to transmit information related to one or more responseconstraints from remote computing server 40 to some or all of thevehicles in fleet 12. For example, one or more response constraints maybe associated with either a particular distributed query, or with futurequeries (e.g., until and unless new response constraints aretransmitted). For example, individual transceivers may be configured toreceive the query information transmitted by distribution component 23.Individual transceivers may be configured to obtain, receive, and/ordetermine response constraints. For example, one or more responseconstraints may be associated with a distributed query and/or includedin transmitted query information.

Query component 24 may be configured to perform queries. For example,for a particular vehicle, query component 24 may perform a query onlocally stored information. In some implementations, a distributed querymay be performed on information that is physically stored in multiplelocations. For example, the information may be stored in two, three, ormore vehicles. The distributed query may be based on query informationreceived by one or more transceivers. Subsequent to performance of adistributed query, one or more sets of potential results may beproduced. Potential results may be converted and/or otherwise processedby conversion component 38 to create the results that will betransmitted. For example, individual transceivers may be configured totransmit results (e.g., converted potential results) from one or morevehicles to remote computing server 40. In some implementations, querycomponent 24 may be configured to perform a distributed query in amanner that is based at least in part on one or more responseconstraints. For example, for urgent and time-limited queries having alimited data budget, high-resolution images and/or high-resolution videomay be a priori excluded from even the potential results.

Conversion component 38 may be configured to convert and/or summarizeone or more potential results into one or more results. For example,conversion component 38 may be configured to convert a set of potentialresults to create a set of results that will be transmitted by atransceiver. Operation by conversion component 38 may be based on one ormore response constraints, one or more current local data transmissionconditions, and/or other conditions. For example, for urgent andtime-limited queries having a limited data budget, conversion component38 may be configured to convert high-resolution images and/orhigh-resolution video in a set of potential results to lower-resolutionimages and/or lower-resolution video to create a set of results fortransmission.

In some implementations, conversion component 38 may be configured toconvert a potential result having a particular format into a resulthaving a different format that uses a smaller amount of data than theoriginal potential result. For example, images captured by image sensorstend to require a larger amount of data than the results after one ormore of computer vision, computer detection, feature extraction, and/orother image processing techniques have been applied to the capturedimages. In some implementations, conversion component 38 may beconfigured to compress a potential result such that the compressedresult uses a smaller amount of data than the original potential result.

In some implementations, operations by vehicle-specific components inresponse to a distributed query may be adjusted and/or controlleddynamically in response to changing data transmission conditions. Forexample, a particular set of resources for a particular vehicle mayreceive a distributed query having a cost limit of $5, which at thecurrent (cellular data) transmission protocol in the local area of theparticular vehicle, given the known data transmission costs, limits theresponse to X minutes of transmission (or a data budget of Y MB ofdata). Based on these constraints, conversion component 38 mayautonomously decide to forego any video, and instead include in the setof results a particular number of snapshots of a particular imagesensor, at pertinent moments in time. However, prior to X minutespassing (or prior to Y MB of data being transmitted in response to thedistributed query), the current transmission protocol may change in amanner that either reduces the cost of data transmission, or improvesthe available bandwidth such that effectively the data budget isincreased. Conversion component 38 may be configured to take advantageof such a transmission protocol change and subsequently changeinformation in the set of results and/or add information to the set ofresults that was previously excluded, such as relevant video clips. Forexample, the original set of response constraints may continue to be ineffect, such as the cost limit of $5. However, due to the real-timechanges, the conversion from the set of potential results to the set ofresults to be transmitted may dynamically change as well. At eachvehicle the operations that provide a response to a distributed querymay be performed independently from any other vehicle. Even vehicleshaving the same or similar sensors, resources, and response constraintsmay respond differently due to localized differences in current localdata transmission conditions. In some implementations, individualvehicles and/or sets of resources included in individual vehicles mayindependently perform the same distributed query based onvehicle-specific quality-of-service considerations and/or guidelines.

Result component 25 may be configured to receive information from one ormore transceivers (and/or from one or more vehicles). For example,result component 25 may receive sets of results produced by querycomponents of different vehicles and/or converted by conversioncomponents of different vehicles. For example, the received informationmay include a first set of results received from the transceiver offirst vehicle 12 a, a second set of results received from thetransceiver of second vehicle 12 b, a third set of results received fromthe transceiver of third vehicle 12 c, and so forth. Individual sets ofresults may have been produced by individual query components and/orconversion components (e.g., instances of query component 24 and/orconversion component 38) distributed across different vehicles in fleet12. For example, different sets of resources may include individualinstances of a query component. For example, different sets of resourcesmay include individual instances of a conversion component.

In some implementations, result component 25 may be configured toreceive information that has been organized into data packets. Forexample, the data packets may be numbered and/or otherwise annotated. Insome implementations, data packets may include error correctioninformation that may be used to determine, upon receipt, if any of thedata in a set of packets is missing and/or corrupted.

Aggregate component 26 may be configured to aggregate informationreceived from different transceivers. The aggregated information may bereferred to as aggregated results. For example, aggregate component 26may be configured to aggregate a first set of results from a firsttransceiver (included in first set of resources 51 a), a second set ofresults from a second transceiver (included in second set of resources51 b), a third set of results from a third transceiver (included inthird set of resources 51 c), and so forth. In some implementations, aparticular query performed for a particular vehicle may produce a zeroresult, or an empty result. These types of results may be aggregatedwith the sets of results from other vehicles in fleet 12. Presentationcomponent 21 may be configured to facilitate presentation of theaggregated results to user 60 of remote computing server 40.

Correction component 27 may be configured to determine whether any ofthe data in a set of data packets is missing and/or corrupted. Forexample, a set of data packets may include error correction information(including but not limited to error-checking codes). In someimplementations, a set of received data packets may include annotations,including but not limited to numbering, such that correction component27 can determine whether any data packets are missing. For example,correction component 27 may determine a particular data packet from aparticular transceiver is missing. For example, correction component 27may determine a different data packet from a different transceiver hasbeen corrupted.

Re-transmit component 28 may be configured to transmit requests forparticular information, such as a particular data packet, to one or moretransceivers. Requests from re-transmit component 28 may be based ondeterminations by correction component 27. For example, re-transmitcomponent 28 may transmit a first request to a particular transceiverfor re-transmission of a particular data packet. For example,re-transmit component 28 may transmit a second request to a differenttransceiver for re-transmission of a different data packet. The firstand second request may be based on determinations by correctioncomponent 27.

Backup component 29 may be configured to facilitate backup of particularinformation in a separate location such that the particular informationis physically stored in more than one location. For example, backupcomponent 29 may select some or all of the information stored in the setof resources for a particular vehicle. For example, backup component 29may select one or more locations suitable for storage that are separateand remote from the particular vehicle. The selected information may betransmitted to the selected locations for storage. For example,subsequent to operations performed by backup component 29, particularinformation may be stored at different locations. Redundant storage asaccomplished through the operations by backup component 29 may improvethe resilience of fleet of vehicles 12 to localized outages, datacorruption, loss, and/or other types of accidents.

Virtualization component 30 may be configured to effectuate managementof distributed sets of resources 55. In some implementations, anindividual distributed set of resources may include resources of thesame or similar type. For example, a first distributed set of resources55 a may include resources for electronic storage of information, asecond distributed set of resources 55 b may include resources thatprovide information-processing capabilities, a third distributed set ofresources 55 c may include resources that provideinformation-distribution capabilities, and so forth. For example, theresources for electronic storage of information may include a first datastore (included in first set of resources 51 a for the first vehicle), asecond data store (included in the second set of resources 51 b for thesecond vehicle), a third data store (included in the third set ofresources 51 c for the third vehicle), and so forth. For example,virtualization component 30 may be configured to manage a distributeddata store that includes data stored in the first data store, the seconddata store, the third data store, and so forth. In some implementations,virtualization component 30 may be configured to effectuate managementof different layers of virtualization of resources. For example, thelowest layer 90 may include the physical resources, a next layer 91 mayinclude the distributed sets of resources, and another next layer 92 mayinclude distributed APIs, distributed applications, and/or servicesavailable to users of remote computing server 40. The API, application,and/or service layer may include support for different types and/orformats of queries, and/or for different operating systems, e.g. throughvirtual machines. In some implementations, virtualization component 40may be configured to support different types of virtualization,including but not limited to server virtualization, desktopvirtualization, application virtualization, network virtualization,storage virtualization, and/or other types of virtualization.

Parameter determination component 31 may be configured to determinecurrent operating conditions and/or vehicle parameters. Parameterdetermination component 31 may determine current operating conditionsand/or vehicle parameters based on the information conveyed by theoutput signals from the sensors and/or other information. The one ormore current operating conditions may be related to the vehicle, theoperation of the vehicle, physical characteristics of the vehicle,and/or other information. In some implementations, parameterdetermination component 31 may be configured to determine one or more ofthe current operating conditions one or more times in an ongoing mannerduring operation of the vehicle.

In some implementations, operating conditions may include vehicleparameters. For example, vehicle parameters may be related to one ormore of an acceleration, a direction of travel, a turn diameter, avehicle speed, an engine speed (e.g. RPM), a duration of time, a closingdistance, a lane departure from an intended travelling lane of thevehicle, a following distance, physical characteristics of the vehicle(such as mass and/or number of axles, for example), a tilt angle of thevehicle, an inclination/declination angle of the vehicle, and/or otherparameters.

The physical characteristics of a vehicle may be physical features of avehicle set during manufacture of the vehicle, during loading of thevehicle, and/or at other times. For example, the one or more vehicleparameters may include a vehicle type (e.g., a car, a bus, a semi-truck,a tanker truck), a vehicle size (e.g., length), a vehicle weight (e.g.,including cargo and/or without cargo), a number of gears, a number ofaxles, a type of load carried by the vehicle (e.g., food items,livestock, construction materials, hazardous materials, an oversizedload, a liquid), vehicle trailer type, trailer length, trailer weight,trailer height, a number of axles, and/or other physical features.

In some implementations, parameter determination component 31 may beconfigured to determine one or more vehicle parameters based on theoutput signals from at least two different sensors. For example,parameter determination component 31 may determine one or more of thevehicle parameters based on output signals from a sensor related to theECM system and an external aftermarket added sensor. In someimplementations, a determination of one or more of the vehicleparameters based on output signals from at least two different sensorsmay be more accurate and/or precise than a determination based on theoutput signals from only one sensor. For example, on an icy surface,output signals from an accelerometer may not convey that a driver of thevehicle is applying the brakes of the vehicle. However, a sensor incommunication with the braking system of the vehicle would convey thatthe driver is applying the brakes. A value of a braking parameter may bedetermined based on the braking sensor information even though theoutput signals from the accelerometer may not convey that the driver isapplying the brakes.

Parameter determination component 31 may be configured to determinevehicle parameters that are not directly measurable by any of theavailable sensors. For example, an inclinometer may not be available tomeasure the road grade, but vehicle speed data as measured by a GPSsystem and/or by a wheel sensor ECM may be combined with accelerometerdata to determine the road grade. If an accelerometer measures a forcethat is consistent with braking, but the vehicle speed remains constant,the parameter component can determine that the measured force is acomponent of the gravity vector that is acting along the longitudinalaxis of the vehicle. By using trigonometry, the magnitude of the gravityvector component can be used to determine the road grade (e.g., pitchangle of the vehicle in respect to the horizontal plane).

In some implementations, one or more of the vehicle parameters may bedetermined one or more times in an ongoing manner during operation ofthe vehicle. In some implementations, one or more of the vehicleparameters may be determined at regular time intervals during operationof the vehicle. The timing of the vehicle parameter determinations(e.g., in an ongoing manner, at regular time intervals, etc.) may beprogrammed at manufacture, obtained responsive to user entry and/orselection of timing information via a user interface and/or a remotecomputing device, and/or may be determined in other ways. The timeintervals of parameter determination may be significantly less (e.g.more frequent) than the time intervals at which various sensormeasurements are available. In such cases, parameter determinationcomponent 31 may estimate vehicle parameters in between the actualmeasurements of the same vehicle parameters by the respective sensors,to the extent that the vehicle parameters are measurable. This may beestablished by means of a physical model that describes the behavior ofvarious vehicle parameters and their interdependency. For example, avehicle speed parameter may be estimated at a rate of 20 times persecond, although the underlying speed measurements are much lessfrequent (e.g., four times per second for ECM speed, one time per secondfor GPS speed). This may be accomplished by integrating vehicleacceleration, as measured by the accelerometer sensor where themeasurements are available 1000 times per second, across time todetermine change in speed that is accumulated over time again for themost recent vehicle speed measurement. The benefit of these morefrequent estimates of vehicle parameters are many and they includeimproved operation of other components of system 100, reduced complexityof downstream logic and system design (e.g., all vehicle parameters areupdated at the same interval, rather than being updating irregularly andat the interval of each respective sensor), and more pleasing (e.g.,“smooth”) presentation of vehicle event recorder data through a userinterface.

Detection component 32 may be configured to detect vehicle events. Insome implementations, vehicle events may be related to current operatingconditions of a vehicle. For example, a vehicle event may be based oncomparing one or more vehicle parameters with one or more thresholds.

In some implementations, detection component 32 may be configured todetect specific driving maneuvers based on one or more of a vehiclespeed, an engine load, a throttle level, an accelerator position,vehicle direction, a gravitational force, and/or other parameters beingsustained at or above threshold levels for pre-determined amounts oftime. In some implementations, an acceleration and/or force thresholdmay be scaled based on a length of time an acceleration and/or force ismaintained, and/or the particular speed the vehicle is travelling.Detection component 32 may be configured such that force maintained overa period of time at a particular vehicle speed may decrease a thresholdforce the longer that the force is maintained. Detection component 32may be configured such that, combined with engine load data, throttledata may be used to determine a risky event, a fuel wasting event,and/or other events.

Storage component 33 may be configured to store information inelectronic storage. For example, the information may be stored in theelectronic storage of a particular vehicle. In some implementations, thestored information may be related to detected vehicle events, determinedvehicle parameters, and/or other information. In some implementations,storage component 33 may be configured to store vehicle event records ofdetected vehicle events in electronic storage.

Derivation component 34 may be configured to determine and/or deriveinformation from other information. For example, derivation component 34may be configured to derive a set of derivative operating conditionsfrom a set of operating conditions that has been determined by parameterdetermination component 31. For example, a derivative operatingcondition may be a number of occurrences of a particular vehicle eventper a time unit. For example, a first derivative operating condition maybe a number of instances of hard braking per hour of drive-time. Thedefinition of “hard braking” may be related to a deceleration meeting adeceleration threshold for a period of time exceeding a timingthreshold. In some implementations, the particular definition used toderive a derivative operating condition may be modified as needed, e.g.by user 60 of remote computing server 40. As another example, aderivative operating condition may be a number of occurrences of aparticular vehicle event per a unit of distance traveled by a vehicle.For example, a second derivative operating condition may be a number ofinstances of swerving per 100 miles of distance traveled by a vehicle.In some implementations, the particular definition used to derive aderivative operating condition such as swerving may be modified asneeded, e.g. by a user of the remote computing server. Derivativeoperating conditions may include logical and/or arithmetic combinationsof one or more operating conditions. In some implementations, derivativeoperating conditions may include combinations of operating conditionsand other derivative operating conditions. For example, a thirdderivative operating condition may be the number of instances of eitherswerving or hard braking that is detected per hour of driving over 50miles per hour (i.e., vehicle events occurring at a lower speed are notincluded in this combination). For example, a fourth derivativeoperating condition may be the number of instances of either swerving orhard braking that is detected per 100 miles of driving over 50 miles perhour (i.e., vehicle events occurring at a lower speed are not includedin this combination). For example, a fifth derivative operatingcondition may be the number of instances of either swerving or hardbraking that is detected per hour of driving within a particulargeographic area (i.e., vehicle events occurring outside this area arenot included in this combination).

Virtual sensor component 35 may be configured to define, create, and/orotherwise effectuate management of virtual sensors. A virtual sensor maybe configured to generate an output signal that conveys informationrelated to a derivative operating condition, including but not limitedto derivative operating conditions from derivation component 34. Forexample, a first virtual sensor may be defined as a sensor that detectsand/or measures the first derivative operating condition, a secondvirtual sensor may be defined as a sensor that detects and/or measuresthe second derivative operating condition, a third virtual sensor may bedefined as a sensor that detects and/or measures the third derivativeoperating condition, a fourth virtual sensor may be defined as a sensorthat detects and/or measures the fourth derivative operating condition,and so forth. In some implementations, individual derivative operatingconditions may be assigned to individual virtual sensors and/or viceversa. In some implementations, storage component 33 may be configuredto store output signals generated by virtual sensors (and/or theinformation conveyed thereby) in electronic storage.

Memory management component 36 may be configured to determine and/ormodify rates of store for sensors and/or virtual sensors. For example, afirst sensor may generate output signals continuously conveying a firstoperating parameter. Memory management component 36 may be configured todetermine at what rate the first operating parameter is stored. Forexample, in case the first operating parameter is speed, the rate ofstorage may be once per second, once per 10 seconds, once per minute,and/or another rate of storage. In some implementations, the rate ofstorage may be adjusted based on the occurrence of one or more vehicleevents. For example, some period of time before and/or after aparticular event (such as a collision), the rate of storage may beincreased to a higher rate (e.g., once per second), whereas outside ofthat period of time before and/or after the particular event, the rateof storage may be decreased to a lower rate (e.g., once a minute). Insome implementations, memory management component 36 may be configuredto allocate previously used storage for reuse. For example, a section ofstorage that was previously used to store a particular operatingparameter at a first rate of storage may be reused partially such that,subsequent to this reuse, the section of storage appears to be used tostore the particular operating parameter at a second rate of storagethat is lower than the first rate of storage. For example, the sectionmay be interleaved with a first set of a first operating parameter(stored at a first rate and generated during a first period) and asecond set of the same operating parameter generated at a second periodsubsequent to the first period. The second set may be stored at the samestorage rate or at a different storage rate. In some implementations,the section may be interleaved with a set of different operatingparameters, which may be stored at the same storage rate, or usingdifferent storage rates.

Scoring component 37 may be configured to determine operator scores thatare specific to vehicle operators. For example, an operator score mayreflect a quality assessment of driving by the vehicle operator. Forexample, an operator score may be based on one or more detected vehicleevents. In some implementations, an operator score may include one ormore scores for safety, timeliness, fuel-efficiency, and/or otherdimensions of a quality assessment. In some implementations, an operatorscore may be based on output generated by one or more virtual sensors.In some implementations, operator scores may be presented to vehicleoperators and/or to users of the remote computing server. In someimplementations, operator scores may be stored for future usage.

In some implementations, one or more components of system 100 may beconfigured to obtain, receive, and/or determine contextual informationrelated to environmental conditions near and/or around vehicles.Environmental conditions may be related to weather conditions, roadsurface conditions, traffic conditions, visibility, and/or otherenvironmental conditions. In some implementations, environmentalconditions may be related to proximity of certain objects that arerelevant to driving, including but not limited to traffic signs,railroad crossings, time of day, ambient light conditions, altitude,and/or other objects relevant to driving. In some implementations,contextual information may include a likelihood of traffic congestionnear a particular vehicle, and/or near a particular location. In someimplementations, contextual information may include a likelihood of theroad surface near a particular vehicle and/or a particular locationbeing icy, wet, and/or otherwise potentially having an effect ofbraking. In some implementations, environmental conditions may includeinformation related to a particular driver and/or a particular trip. Forexample, with every passing hour that a particular driver drives hisvehicle during a particular trip, the likelihood of drowsiness mayincrease. In some implementations, the function between trip duration ordistance and likelihood of drowsiness may be driver-specific.

In some implementations, one or more environmental conditions may bereceived from one or more sources external to the vehicle. For example,a source external to the vehicle may include one or more externalproviders 18. For example, contextual information related to weatherconditions may be received from a particular external provider 18 thatprovides weather information. For example, contextual informationrelated to road surface conditions may be received from a particularexternal provider 18 that provides road condition information. Forexample, contextual information related to traffic conditions may bereceived from a particular external provider 18 that provides trafficinformation.

In some implementations, detection of vehicle events may further bebased one or more types of contextual information. In someimplementations, detection may be accomplished and/or performed at thevehicle. In some implementations, a value of a current operatingcondition that effectuates detection of a vehicle event and/ordetermination of an event type may vary as a function of the contextualinformation. For example, a speed of 50 mph (in a particulargeographical location) may not effectuate detection of a vehicle eventand/or determination of an event type when the road surface is dryand/or when traffic is light, but the same speed in the samegeographical location may effectuate detection of a vehicle event and/ordetermination of an event type responsive to contextual informationand/or other information indicating that the road surface is wet and/oricy (and/or may be wet and/or icy), or responsive to contextualinformation (and/or other information) that traffic is heavy (and/or maybe heavy). In this example, the contextual information (and/or otherinformation) may have an effect of the detection of vehicle eventsand/or the determination of event types. In some implementations,contextual information (and/or other information) may modify thesensitivity of the process and/or mechanism by which vehicle events aredetected and/or event types are determined. In some implementations,detection of vehicle events and/or determination of event types may bebased on one or more comparisons of the values of current operatingconditions with threshold values. In some implementations, a particularthreshold value may vary as a function of contextual information. Insome implementations, a particular threshold value may vary as afunction of other information, e.g. as determined based on sensoroutput.

By way of non-limiting example, lateral forces of about −0.3 g (e.g.,swerve left) and/or about +0.3 g (e.g., swerve right) may be a basisused to detect a swerve. In some implementations, the −0.3 g and/or +0.3g criteria may be used at the vehicle speeds less than about 10 kph. The−0.3 g and/or +0.3 g criteria may be scaled as the vehicle increases inspeed. In some implementations, the −0.3 g and/or +0.3 g criteria may bescaled (e.g., reduced) by about 0.0045 g per kph of speed over 10 kph.To prevent too much sensitivity, the lateral force criteria may belimited to about +/−0.12 g, regardless of the speed of the vehicle, forexample. In some implementations, the criterion for the given period oftime between swerves may be about 3 seconds.

Electronic storage 119 may comprise electronic storage media thatelectronically stores information. The electronic storage media ofelectronic storage 119 may comprise one or both of system storage thatis provided integrally (i.e., substantially non-removable) with system100 and/or removable storage that is removably connectable to system 100via, for example, a port (e.g., a USB port, a firewire port, etc.) or adrive (e.g., a disk drive, etc.). Electronic storage 119 may compriseone or more of optically readable storage media (e.g., optical disks,etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 119 may store software algorithms, recordedvideo event data, information determined by processor 104, informationreceived via a user interface, and/or other information that enablessystem 100 to function properly. Electronic storage 119 may be (in wholeor in part) a separate component within system 100, or electronicstorage 119 may be provided (in whole or in part) integrally with one ormore other components of system 100.

As described above, processor 104 may be configured to provideinformation-processing capabilities in system 100. As such, processor104 may comprise one or more of a digital processor, an analogprocessor, a digital circuit designed to process information, an analogcircuit designed to process information, a state machine, and/or othermechanisms for electronically processing information. Although processor104 is shown in FIG. 1 as a single entity, this is for illustrativepurposes only. In some implementations, processor 104 may comprise aplurality of processing units. These processing units may be physicallylocated within the same device (e.g., a vehicle event recorder), orprocessor 104 may represent processing functionality of a plurality ofdevices operating in coordination.

Processor 110 may be configured to execute components 21-38 by software;hardware; firmware; some combination of software, hardware, and/orfirmware; and/or other mechanisms for configuring processingcapabilities on processor 110. It should be appreciated that althoughcomponents 21-38 are illustrated in FIG. 1 as being co-located within asingle processing unit, in implementations in which processor 104comprises multiple processing units, one or more of components 21-38 maybe located remotely from the other components. The description of thefunctionality provided by the different components 21-38 describedherein is for illustrative purposes, and is not intended to be limiting,as any of components 21-38 may provide more or less functionality thanis described. For example, one or more of components 21-38 may beeliminated, and some or all of its functionality may be provided byother components 21-38. As another example, processor 104 may beconfigured to execute one or more additional components that may performsome or all of the functionality attributed below to one of components21-38.

FIGS. 4A-4B-4C illustrate a method 1000 to capture information based ondetected vehicle events. The operations of method 1000 presented beloware intended to be illustrative. In some implementations, method 1000may be accomplished with one or more additional operations notdescribed, and/or without one or more of the operations discussed.Additionally, the order in which the operations of method 1000 areillustrated (in FIGS. 4A-4B-4C) and described below is not intended tobe limiting. In some implementations, two or more of the operations mayoccur substantially simultaneously.

In some implementations, method 1000 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 1000 in response to instructions storedelectronically on one or more electronic storage mediums. The one ormore processing devices may include one or more devices configuredthrough hardware, firmware, and/or software to be specifically designedfor execution of one or more of the operations of method 1000.

Referring to FIGS. 4A-4B-4C and method 1000, at an operation 1002,output signals are generated, by a first set of sensors, conveying firstinformation related to operation of the first vehicle. The first set ofsensors is carried by the first vehicle. The first information mayinclude first timing information and first operator information. Thefirst timing information associates the generated output signals withone or more first moments of generation by the first set of sensors. Thefirst operator information associates the generated output signals witha first vehicle operator of the first vehicle at the one or more firstmoments of operation. In some embodiments, operation 1002 is performedby a set of sensors the same as or similar to first set of sensors 52 a(shown in FIG. 1 and described herein).

At an operation 1004, the first information is stored, by a first set ofresources carried by the first vehicle. In some embodiments, operation1004 is performed by a set of resources the same as or similar to firstset of resources 51 a (shown in FIG. 1 and described herein).

At an operation 1006, output signals are generated, by a second set ofsensors, conveying second information related to operation of the secondvehicle. The second set of sensors is carried by the second vehicle. Thesecond information may include second timing information and secondoperator information. The second timing information associates thegenerated output signals with one or more second moments of generationby the second set of sensors. The second operator information associatesthe generated output signals with a second vehicle operator of thesecond vehicle at the one or more second moments of operation. In someembodiments, operation 1006 is performed by a set of sensors the same asor similar to second set of sensors 52 b (shown in FIG. 1 and describedherein).

At an operation 1008, the second information is stored, by a second setof resources carried by the second vehicle. In some embodiments,operation 1008 is performed by a set of resources the same as or similarto second set of resources 51 b (shown in FIG. 1 and described herein).

At an operation 1010, output signals are generated, by a third set ofsensors, conveying third information related to operation of the thirdvehicle. The third set of sensors is carried by the third vehicle. Thethird information may include third timing information and thirdoperator information. The third timing information associates thegenerated output signals with one or more third moments of generation bythe third set of sensors. The third operator information associates thegenerated output signals with a third vehicle operator of the thirdvehicle at the one or more third moments of operation. In someembodiments, operation 1010 is performed by a set of sensors the same asor similar to third set of sensors 52 c (shown in FIG. 1 and describedherein).

At an operation 1012, the third information is stored, by a third set ofresources carried by the third vehicle. In some embodiments, operation1012 is performed by a set of resources the same as or similar to thirdset of resources 51 c (shown in FIG. 1 and described herein).

At an operation 1014, presentation of a user interface to a user isfacilitated, by a remote computing server that is separate and discretefrom the fleet of vehicles. In some embodiments, operation 1014 isperformed by a presentation component the same as or similar topresentation component 21 (shown in FIG. 1 and described herein).

At an operation 1016, input is received from the user through the userinterface. The received input represents a distributed query related tothe operation of the fleet of vehicles. In some embodiments, operation1016 is performed by an interface component the same as or similar tointerface component 22 (shown in FIG. 1 and described herein).

At an operation 1018, query information is transmitted, at least in partwirelessly, from the remote computing server to a subset of the fleet ofvehicles. The subset includes the first, second, and third vehicle. Thequery information is based on the distributed query. In someembodiments, operation 1018 is performed by a distribution component thesame as or similar to distribution component 23 (shown in FIG. 1 anddescribed herein).

At an operation 1020, the query information is received, by a firsttransceiver included in the first set of resources, from the remotecomputing server. In some embodiments, operation 1020 is performed by aset of resources the same as or similar to first set of resources 51 a(shown in FIG. 1 and described herein).

At an operation 1022, the query information is received, by a secondtransceiver included in the second set of resources, the queryinformation from the remote computing server. In some embodiments,operation 1022 is performed by a set of resources the same as or similarto second set of resources 51 b (shown in FIG. 1 and described herein).

At an operation 1024, the query information is received, by a thirdtransceiver included in the third set of resources, the queryinformation from the remote computing server. In some embodiments,operation 1024 is performed by a set of resources the same as or similarto third set of resources 51 c (shown in FIG. 1 and described herein).

At an operation 1026, the distributed query is performed, by the firstset of resources, based on the received query information. Performanceresults in a first set of potential results. In some embodiments,operation 1026 is performed by a query component the same as or similarto query component 24 (shown in FIG. 1 and described herein).

At an operation 1027, the distributed query is performed, by the secondset of resources, based on the received query information. Performanceresults in a second set of potential results. In some embodiments,operation 1027 is performed by a query component the same as or similarto query component 24 (shown in FIG. 1 and described herein).

At an operation 1028, the distributed query is performed, by the thirdset of resources, based on the received query information. Performanceresults in a third set of potential results. In some embodiments,operation 1028 is performed by a query component the same as or similarto query component 24 (shown in FIG. 1 and described herein).

At an operation 1029, the first set of potential results is converted,by the first set of resources, to create a first set of results. Theconversion is based on a first set of response constraints and firstcurrent local data transmission conditions. In some embodiments,operation 1029 is performed by a conversion component the same as orsimilar to conversion component 38 (shown in FIG. 1 and describedherein).

At an operation 1030, the second set of potential results is converted,by the second set of resources, to create a second set of results. Theconversion is based on a second set of response constraints and secondcurrent local data transmission conditions. In some embodiments,operation 1030 is performed by a conversion component the same as orsimilar to conversion component 38 (shown in FIG. 1 and describedherein).

At an operation 1031, the third set of potential results is converted,by the third set of resources, to create a third set of results. Theconversion is based on a third set of response constraints and thirdcurrent local data transmission conditions. In some embodiments,operation 1031 is performed by a conversion component the same as orsimilar to conversion component 38 (shown in FIG. 1 and describedherein).

At an operation 1032, the first set of results is transmitted to theremote computing server. In some embodiments, operation 1032 isperformed by a set of resources the same as or similar to first set ofresources 51 a (shown in FIG. 1 and described herein).

At an operation 1034, the second set of results is transmitted to theremote computing server. In some embodiments, operation 1034 isperformed by a set of resources the same as or similar to second set ofresources 51 b (shown in FIG. 1 and described herein).

At an operation 1036, the third set of results is transmitted to theremote computing server. In some embodiments, operation 1036 isperformed by a set of resources the same as or similar to third set ofresources 51 c (shown in FIG. 1 and described herein).

At an operation 1038, the first set of results is received by the remotecomputing server from the first transceiver, the second set of resultsis received from the second transceiver, and the third set of results isreceived from the third transceiver. In some embodiments, operation 1038is performed by a result component the same as or similar to resultcomponent 25 (shown in FIG. 1 and described herein).

At an operation 1040, the first, second, and third set of results areaggregated, by the remote computing server, into aggregated results. Insome embodiments, operation 1040 is performed by an aggregate componentthe same as or similar to aggregate component 26 (shown in FIG. 1 anddescribed herein).

At an operation 1042, presentation of the aggregated results isfacilitated, by the remote computing server, via the user interface tothe user. In some embodiments, operation 1042 is performed by apresentation component the same as or similar to presentation component21 (shown in FIG. 1 and described herein).

In some implementations, system 100 is configured to use data-processingresources carried by a fleet of vehicles as a distributed data center,system 100 configured to couple with the fleet of at least 5 vehicles,the system comprising elements carried by and/or included in individualones of the vehicles in the fleet operating jointly with a remotecomputing server. Individual ones of the vehicles in the fleet include aset of resources for data processing, wherein the set of resourcesincludes a transceiver configured to transfer and receive information toand from the remote computing server. The individual ones of thevehicles in the fleet further include a set of sensors configured togenerate output signals conveying information related to operation ofeach vehicle. The remote computing server is separate and discrete fromthe fleet of vehicles and includes one or more processors configured to:facilitate presentation of a user interface to a user, which receiveinput from the user, wherein the received input represents a distributedquery related to the operation of the fleet of vehicles; and transmitthe distributed query to the fleet. Individual sets of resourcesincluded in individual vehicles are further configured to: obtain a setof response constraints; obtain current local data transmissionconditions; perform the distributed query for an individual vehicle,resulting in a set of potential results; and convert the set ofpotential results to create a set of results, wherein conversion isbased on the set of response constraints and the current local datatransmission conditions. Individual sets of results are transmitted tothe remote computing server, which receives and aggregates theindividual sets of results, and presents the aggregated results via theuser interface to the user.

Although the system(s) and/or method(s) of this disclosure have beendescribed in detail for the purpose of illustration based on what iscurrently considered to be the most practical and preferredimplementations, it is to be understood that such detail is solely forthat purpose and that the disclosure is not limited to the disclosedimplementations, but, on the contrary, is intended to covermodifications and equivalent arrangements that are within the spirit andscope of the appended claims. For example, it is to be understood thatthe present disclosure contemplates that, to the extent possible, one ormore features of any implementation can be combined with one or morefeatures of any other implementation.

What is claimed is:
 1. A system configured to use data-processingresources carried by a fleet of vehicles, the system configured tocouple with the fleet of vehicles, wherein the fleet includes multiplevehicles, the system comprising: one or more storage servers includingone or more processors, wherein the one or more storage servers areseparate and discrete from the fleet of vehicles, wherein the one ormore storage servers are configured to electronically store information,wherein the information is received from the fleet of vehicles; and acomputing server including one or more processors, wherein the computingserver is separate and discrete from the fleet of vehicles, and whereinthe one or more processors are configured via machine-readableinstructions to: receive a query from a user, wherein the query is to beperformed on at least one of (a) vehicle-specific sensor data and (b)vehicle-specific information derived from the vehicle-specific sensordata, wherein the vehicle-specific data has been captured by sensors onindividual vehicles in the fleet of vehicles and wherein at least one of(a) the vehicle-specific sensor data and (b) the vehicle-specificinformation derived from the vehicle-specific sensor data is stored onthe one or more storage servers; transmit, to the one or more storageservers, query information that is based on the query, wherein the queryinformation instructs to: (i) perform the query on at least one of (a)the vehicle-specific sensor data that is stored on the one or morestorage servers and (b) the vehicle-specific information derived fromthe vehicle-specific sensor data that is stored on the one or morestorage servers, resulting in the individual sets of potential results,and (ii) constrain the individual sets of potential results to createindividual sets of results, wherein said constraining is based on usingone or more sets of response constraints, wherein said constraining ofthe individual sets of potential results is performed such that anamount of bandwidth required to transmit the individual sets of resultsis reduced compared to the individual sets of potential results; obtainthe individual sets of results from the one or more storage servers; andfacilitate a presentation based on the individual sets of results,wherein the presentation is presented to the user via the userinterface.
 2. The system of claim 1, wherein the query corresponds toone or more particular time frames, wherein performance of the query islimited to the vehicle-specific sensor data that was captured in the oneor more particular time frames by the sensors that are carried by theindividual vehicles.
 3. The system of claim 1, wherein at least part ofthe sets of response constraints are determined based on the queryinformation.
 4. The system of claim 1, wherein the query corresponds toa particular vehicle operator.
 5. The system of claim 1, wherein theindividual sets of results are received in annotated data packets,wherein the one or more processors of the computing server are furtherconfigured to: determine whether one or more particular data packets aremissing or corrupted, based on annotations in the annotated datapackets; and responsive to a determination that the one or moreparticular data packets are missing or corrupted, transmit a request tore-transmit the one or more particular data packets.
 6. The system ofclaim 1, wherein the one or more storage servers are configured bymachine-readable instructions to: determine a first set of derivativeoperating information, wherein the first set of derivative operatinginformation is derived from the vehicle-specific sensor data; and storethe first set of derivative operating information.
 7. The system ofclaim 1, wherein the query is received from the user through a userinterface.
 8. The system of claim 1, wherein the query further instructsto obtain the one or more sets of response constraints.
 9. The system ofclaim 1, wherein said constraining is based on at least one of (a)summarizing and (b) adjusting a rate of generation and/or capture for atleast one of the sensors.
 10. A method to use data-processing resourcescarried by a fleet of vehicles, wherein the fleet includes multiplevehicles, the method comprising: storing information electronically, onone or more storage servers, wherein the information is received fromthe fleet of vehicles; receiving a query from a user, wherein the queryis to be performed on at least one of (a) vehicle-specific sensor dataand (b) vehicle-specific information derived from the vehicle-specificsensor data, wherein the vehicle-specific data has been captured bysensors on individual vehicles in the fleet of vehicles and wherein atleast one of (a) the vehicle-specific sensor data and (b) thevehicle-specific information derived from the vehicle-specific sensordata is stored on the one or more storage servers; transmitting, to theone or more storage servers, query information that is based on thequery, wherein the query information instructs to: (i) perform the queryon at least one of (a) the vehicle-specific sensor data that is storedon the one or more storage servers and (b) the vehicle-specificinformation derived from the vehicle-specific sensor data that is storedon the one or more storage servers, (ii) constrain the individual setsof potential results to create individual sets of results, wherein saidconstraining is based on using one or more sets of response constraints,wherein said constraining of the individual sets of potential results isperformed such that an amount of bandwidth required to transmit theindividual sets of results is reduced compared to the individual sets ofpotential results; obtaining, by a computing server that is separate anddiscrete from the fleet of vehicles, the individual sets of results fromthe one or more storage servers; and facilitating, by the computingserver, a presentation based on the individual sets of results, whereinthe presentation is presented to the user via the user interface.